Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 195ee66cbacf920623d4e3c4784c95cd3c4693b5b66a8b4ecf3daf777109ccc7

Tx prefix hash: cc27a296df4c5edec0168285c945f69bf16240f06f072662725551e894860784
Tx public key: 3ee0829f1a17ad0088fc9b91a0b6afab77e864e193af5a4c86e901a65b4f6057
Timestamp: 1618454632 Timestamp [UCT]: 2021-04-15 02:43:52 Age [y:d:h:m:s]: 04:002:08:16:19
Block: 240096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1022570 RingCT/type: yes/0
Extra: 013ee0829f1a17ad0088fc9b91a0b6afab77e864e193af5a4c86e901a65b4f60570211000000023634f08d000000000000000000

1 output(s) for total of 98.279480342000 dcy

stealth address amount amount idx
00: e0994eae6a56ad1d81da23fa06ec3ea79cacd74536d9fb1c55a47c67f96b40e1 98.279480342000 500250 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": 240106, "vin": [ { "gen": { "height": 240096 } } ], "vout": [ { "amount": 98279480342, "target": { "key": "e0994eae6a56ad1d81da23fa06ec3ea79cacd74536d9fb1c55a47c67f96b40e1" } } ], "extra": [ 1, 62, 224, 130, 159, 26, 23, 173, 0, 136, 252, 155, 145, 160, 182, 175, 171, 119, 232, 100, 225, 147, 175, 90, 76, 134, 233, 1, 166, 91, 79, 96, 87, 2, 17, 0, 0, 0, 2, 54, 52, 240, 141, 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