Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead6ff8dc180bb489db942dc1c31e012a15e37aea09c6e101cd9baa2e58544f1

Tx prefix hash: ef6f7c67f77c594166b53bc199887d2fdca2d3c71eea860879a704867364cd6f
Tx public key: bc53f396f2fdb14afd0913d45f4de5d96990ef8d4cbe5dd140ca547c5cbe5a4a
Timestamp: 1677675798 Timestamp [UCT]: 2023-03-01 13:03:18 Age [y:d:h:m:s]: 01:277:01:25:54
Block: 707547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458921 RingCT/type: yes/0
Extra: 01bc53f396f2fdb14afd0913d45f4de5d96990ef8d4cbe5dd140ca547c5cbe5a4a02110000000175e3f0e9000000000000000000

1 output(s) for total of 2.777173257000 dcy

stealth address amount amount idx
00: 14e0d4e6a0c6e9747c0d336a723398f591cffaf625372af88a8a5972f32699c0 2.777173257000 1151360 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": 707557, "vin": [ { "gen": { "height": 707547 } } ], "vout": [ { "amount": 2777173257, "target": { "key": "14e0d4e6a0c6e9747c0d336a723398f591cffaf625372af88a8a5972f32699c0" } } ], "extra": [ 1, 188, 83, 243, 150, 242, 253, 177, 74, 253, 9, 19, 212, 95, 77, 229, 217, 105, 144, 239, 141, 76, 190, 93, 209, 64, 202, 84, 124, 92, 190, 90, 74, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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