Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bb98d322f10b165bcf378bfc08288ebed0421450ccdb7d0fae6e41da98a4b15

Tx prefix hash: 7c03704c95e56d0ec8b60d3394104e97d469e8094a17ed997c724d2dd869fe3e
Tx public key: bc470ba82a15b7aad071b1f58169e6e372b4e425d500d1c94bf7b095065c4a46
Timestamp: 1713136238 Timestamp [UCT]: 2024-04-14 23:10:38 Age [y:d:h:m:s]: 00:338:11:33:49
Block: 1000634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242016 RingCT/type: yes/0
Extra: 01bc470ba82a15b7aad071b1f58169e6e372b4e425d500d1c94bf7b095065c4a4602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92af22086a0617938f7c805c573a2790bdd840490f0c9f1c2dd01b4aeeaa4d49 0.600000000000 1461132 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": 1000644, "vin": [ { "gen": { "height": 1000634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92af22086a0617938f7c805c573a2790bdd840490f0c9f1c2dd01b4aeeaa4d49" } } ], "extra": [ 1, 188, 71, 11, 168, 42, 21, 183, 170, 208, 113, 177, 245, 129, 105, 230, 227, 114, 180, 228, 37, 213, 0, 209, 201, 75, 247, 176, 149, 6, 92, 74, 70, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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