Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80867699ada1ad278334116cb6d88dccf8b38bcc3da8a6baf1dcf0b905903754

Tx prefix hash: 58962212170e085ea7c6edd63526ee8e3e5870aefe5e350cba76396297245a58
Tx public key: f7d2d5615b8b037eea98e2856c40dd3db843a520f21be35ae2d80d265815dff8
Timestamp: 1732806866 Timestamp [UCT]: 2024-11-28 15:14:26 Age [y:d:h:m:s]: 00:123:04:45:11
Block: 1163639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87848 RingCT/type: yes/0
Extra: 01f7d2d5615b8b037eea98e2856c40dd3db843a520f21be35ae2d80d265815dff80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d0307188e5518aefebe260fd62b3e43f58388595e090130edae4b034ea853c9 0.600000000000 1649306 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": 1163649, "vin": [ { "gen": { "height": 1163639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d0307188e5518aefebe260fd62b3e43f58388595e090130edae4b034ea853c9" } } ], "extra": [ 1, 247, 210, 213, 97, 91, 139, 3, 126, 234, 152, 226, 133, 108, 64, 221, 61, 184, 67, 165, 32, 242, 27, 227, 90, 226, 216, 13, 38, 88, 21, 223, 248, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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