Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77f07809e3bedfe04f32cdead36fddd8a734b0e1c7be3a40988918f8283181d6

Tx prefix hash: 6de83348223469e2088e17f40b0f70a17d347e4e1ef810ecb01bdd254e24e17a
Tx public key: 75c946bdda40f6a6b9042340d57dead01a05f1fab52306830e15bc7a21612583
Timestamp: 1647036838 Timestamp [UCT]: 2022-03-11 22:13:58 Age [y:d:h:m:s]: 02:238:23:30:46
Block: 456386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690255 RingCT/type: yes/0
Extra: 0175c946bdda40f6a6b9042340d57dead01a05f1fab52306830e15bc7a21612583021100000011c9067537000000000000000000

1 output(s) for total of 18.871394633000 dcy

stealth address amount amount idx
00: 2b6b25ede114bd819c2f3a5bbcd8028575968aacf9e4f1de38af6e90d73c54c8 18.871394633000 872433 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": 456396, "vin": [ { "gen": { "height": 456386 } } ], "vout": [ { "amount": 18871394633, "target": { "key": "2b6b25ede114bd819c2f3a5bbcd8028575968aacf9e4f1de38af6e90d73c54c8" } } ], "extra": [ 1, 117, 201, 70, 189, 218, 64, 246, 166, 185, 4, 35, 64, 213, 125, 234, 208, 26, 5, 241, 250, 181, 35, 6, 131, 14, 21, 188, 122, 33, 97, 37, 131, 2, 17, 0, 0, 0, 17, 201, 6, 117, 55, 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