Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0854a710c604b4886f983074ed042f0a030520b1eb8d9f63aead6da6f172c84e

Tx prefix hash: a9cb098d0801d5ebfc03a641aaf010cc69abc8d631a2b55941b8ea8b9589af1f
Tx public key: 748f843e8c20d211869e5b2c5cce5b2375e97f1fa16ef0e51244691e6f33f8d9
Timestamp: 1688991709 Timestamp [UCT]: 2023-07-10 12:21:49 Age [y:d:h:m:s]: 01:187:13:37:24
Block: 800746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395401 RingCT/type: yes/0
Extra: 01748f843e8c20d211869e5b2c5cce5b2375e97f1fa16ef0e51244691e6f33f8d9021100000005faf35c9c000000000000000000

1 output(s) for total of 1.363943013000 dcy

stealth address amount amount idx
00: bb79d5bf705ed1e67957592018a88b5af3ef75f49221eb7c7345d0561dc3d2e6 1.363943013000 1251809 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 800756, "vin": [ { "gen": { "height": 800746 } } ], "vout": [ { "amount": 1363943013, "target": { "key": "bb79d5bf705ed1e67957592018a88b5af3ef75f49221eb7c7345d0561dc3d2e6" } } ], "extra": [ 1, 116, 143, 132, 62, 140, 32, 210, 17, 134, 158, 91, 44, 92, 206, 91, 35, 117, 233, 127, 31, 161, 110, 240, 229, 18, 68, 105, 30, 111, 51, 248, 217, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8