Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12ed31ebb54c16b1d9bba19061612e1b358df90fc7e15bcc025b6d1bd2609885

Tx prefix hash: eb95dd7a63e158a2cd0aa8426f25a9e2148a783ff0ac4aaee8d896a92be56c58
Tx public key: 10124d1133a535882b653d31806ca3ddcc35f7eac3f1a6747e794ce4c5bf6139
Timestamp: 1694284651 Timestamp [UCT]: 2023-09-09 18:37:31 Age [y:d:h:m:s]: 01:220:23:59:11
Block: 844543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419048 RingCT/type: yes/0
Extra: 0110124d1133a535882b653d31806ca3ddcc35f7eac3f1a6747e794ce4c5bf613902110000000375e3f0e9000000000000000000

1 output(s) for total of 0.976514101000 dcy

stealth address amount amount idx
00: fbc4b800f120a70fbdcd3f3328f9c663656f02017ad6ecfcd39b9519aacf26dc 0.976514101000 1297857 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": 844553, "vin": [ { "gen": { "height": 844543 } } ], "vout": [ { "amount": 976514101, "target": { "key": "fbc4b800f120a70fbdcd3f3328f9c663656f02017ad6ecfcd39b9519aacf26dc" } } ], "extra": [ 1, 16, 18, 77, 17, 51, 165, 53, 136, 43, 101, 61, 49, 128, 108, 163, 221, 204, 53, 247, 234, 195, 241, 166, 116, 126, 121, 76, 228, 197, 191, 97, 57, 2, 17, 0, 0, 0, 3, 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