Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b458853f002e61d63cd958734ea2aefe31502dc22c33459944e0b4f0461b5f0

Tx prefix hash: 18d14a4094af67584fac9c37b139c3acb8e9635223699c0826cefb7352913d75
Tx public key: ee213b251499fdc77d3cc248a2fc369d1741af3798cd187b98061794d1a3a3fe
Timestamp: 1648259492 Timestamp [UCT]: 2022-03-26 01:51:32 Age [y:d:h:m:s]: 02:227:17:11:22
Block: 466487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 682233 RingCT/type: yes/0
Extra: 01ee213b251499fdc77d3cc248a2fc369d1741af3798cd187b98061794d1a3a3fe02110000000c4a0f5013000000000000000000

1 output(s) for total of 17.471700469000 dcy

stealth address amount amount idx
00: e8eee4c5af1e36b547b72db464782aa2b7f87044a1f0749b38d50bee718fb5b1 17.471700469000 884810 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": 466497, "vin": [ { "gen": { "height": 466487 } } ], "vout": [ { "amount": 17471700469, "target": { "key": "e8eee4c5af1e36b547b72db464782aa2b7f87044a1f0749b38d50bee718fb5b1" } } ], "extra": [ 1, 238, 33, 59, 37, 20, 153, 253, 199, 125, 60, 194, 72, 162, 252, 54, 157, 23, 65, 175, 55, 152, 205, 24, 123, 152, 6, 23, 148, 209, 163, 163, 254, 2, 17, 0, 0, 0, 12, 74, 15, 80, 19, 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