Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 812b966379bd9f2e9b048d412218b16e63a776945e41bd2510b84ff8b3098bc1

Tx prefix hash: 56fab6c8180384922ca7ac50f70ad8d3b5dc4e169c4bcca80e42473babb5d2ec
Tx public key: c5fb22f1f4e54011e1d2595b7ef5bd275f349e99d8256e7dd96dffe5d609313b
Timestamp: 1726248516 Timestamp [UCT]: 2024-09-13 17:28:36 Age [y:d:h:m:s]: 00:071:13:51:05
Block: 1109355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51177 RingCT/type: yes/0
Extra: 01c5fb22f1f4e54011e1d2595b7ef5bd275f349e99d8256e7dd96dffe5d609313b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 530e947f2b818c8d6edcda94a6d69bbf4ddbb02571c5d010c3ea3fbeb9a3b8b3 0.600000000000 1587576 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": 1109365, "vin": [ { "gen": { "height": 1109355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "530e947f2b818c8d6edcda94a6d69bbf4ddbb02571c5d010c3ea3fbeb9a3b8b3" } } ], "extra": [ 1, 197, 251, 34, 241, 244, 229, 64, 17, 225, 210, 89, 91, 126, 245, 189, 39, 95, 52, 158, 153, 216, 37, 110, 125, 217, 109, 255, 229, 214, 9, 49, 59, 2, 17, 0, 0, 0, 4, 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