Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c2b588ffad1b059176f4b799abf8563bcbdcd39920f896cb80eee8bf9c30cfe

Tx prefix hash: b3f911938d9530614406cf64b15f7d4daee188b1656828fba9aa1da27c6aabe1
Tx public key: fbe8434a1b3a7cfbf1a8a13e9bc695f881f3b4a1c3f8a8bb52cd3c8aab66f22b
Timestamp: 1656505071 Timestamp [UCT]: 2022-06-29 12:17:51 Age [y:d:h:m:s]: 02:230:03:12:50
Block: 532886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685573 RingCT/type: yes/0
Extra: 01fbe8434a1b3a7cfbf1a8a13e9bc695f881f3b4a1c3f8a8bb52cd3c8aab66f22b02110000000633af99f4000000000000000000

1 output(s) for total of 10.529307638000 dcy

stealth address amount amount idx
00: b2a993e5a294048e13f9ff19ad9aaacbaba47ef937da51e53da5de030037f856 10.529307638000 962157 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": 532896, "vin": [ { "gen": { "height": 532886 } } ], "vout": [ { "amount": 10529307638, "target": { "key": "b2a993e5a294048e13f9ff19ad9aaacbaba47ef937da51e53da5de030037f856" } } ], "extra": [ 1, 251, 232, 67, 74, 27, 58, 124, 251, 241, 168, 161, 62, 155, 198, 149, 248, 129, 243, 180, 161, 195, 248, 168, 187, 82, 205, 60, 138, 171, 102, 242, 43, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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