Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dec398bcf47682c20e4ea36fd3c51c30ffdf28029d22b4a5828ff83421291c0

Tx prefix hash: 248fea2eed0f6cd60fb5c37135fbecec2e86ec1953c513b586ff3c08d405d530
Tx public key: 34bd0f3001ec2eaebc9df590cff8c2988321b42d305b073fbcd8cc841dd50f5e
Timestamp: 1723222570 Timestamp [UCT]: 2024-08-09 16:56:10 Age [y:d:h:m:s]: 00:277:09:29:31
Block: 1084279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198159 RingCT/type: yes/0
Extra: 0134bd0f3001ec2eaebc9df590cff8c2988321b42d305b073fbcd8cc841dd50f5e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 285bb06410b33ba446a9c34b5c44364f76f28d824a864263e856d563304d0f23 0.600000000000 1558496 of 15

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": 1084289, "vin": [ { "gen": { "height": 1084279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "285bb06410b33ba446a9c34b5c44364f76f28d824a864263e856d563304d0f23" } } ], "extra": [ 1, 52, 189, 15, 48, 1, 236, 46, 174, 188, 157, 245, 144, 207, 248, 194, 152, 131, 33, 180, 45, 48, 91, 7, 63, 188, 216, 204, 132, 29, 213, 15, 94, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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