Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 613ea3f4782f2996dfb1114921becd59195e2c2f1d2322be4e7d364d7dd2886a

Tx prefix hash: deba1843d4272d18edc61d7eb9f8707ccf79b25d7becf5d16196cb0798d68aa1
Tx public key: 157b0ccafa7dee1a57aeb0e441b6568dfac0ef48c6f864e52154c6aebbd7796a
Timestamp: 1671138704 Timestamp [UCT]: 2022-12-15 21:11:44 Age [y:d:h:m:s]: 02:090:03:43:55
Block: 653363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586133 RingCT/type: yes/0
Extra: 01157b0ccafa7dee1a57aeb0e441b6568dfac0ef48c6f864e52154c6aebbd7796a0211000000017e406890000000000000000000

1 output(s) for total of 4.198915537000 dcy

stealth address amount amount idx
00: a317e5ba19104b7bbf2dcfdfef39112165335cbe2c7efdac822c2981ec07a1ae 4.198915537000 1093826 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": 653373, "vin": [ { "gen": { "height": 653363 } } ], "vout": [ { "amount": 4198915537, "target": { "key": "a317e5ba19104b7bbf2dcfdfef39112165335cbe2c7efdac822c2981ec07a1ae" } } ], "extra": [ 1, 21, 123, 12, 202, 250, 125, 238, 26, 87, 174, 176, 228, 65, 182, 86, 141, 250, 192, 239, 72, 198, 248, 100, 229, 33, 84, 198, 174, 187, 215, 121, 106, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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