Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2151184e91964188a3a736ec30fc757dfb8ba860c92ce70581842527da43bba

Tx prefix hash: 3a1cb13acf530232f4d7420012d7c6689bc022117088f03c5f8d6d85f32d768c
Tx public key: 04870bf839ba4e2ae571799e93b1483aebf8d0d38f7acd08408ac6046ea274c4
Timestamp: 1684761450 Timestamp [UCT]: 2023-05-22 13:17:30 Age [y:d:h:m:s]: 01:349:05:22:23
Block: 765674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510805 RingCT/type: yes/0
Extra: 0104870bf839ba4e2ae571799e93b1483aebf8d0d38f7acd08408ac6046ea274c402110000000675e3f0e9000000000000000000

1 output(s) for total of 1.782396710000 dcy

stealth address amount amount idx
00: 65cabfaf8d60feabf57b22df8ea2e0dcdf891f30a5451b89f05737a6d693889e 1.782396710000 1214671 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": 765684, "vin": [ { "gen": { "height": 765674 } } ], "vout": [ { "amount": 1782396710, "target": { "key": "65cabfaf8d60feabf57b22df8ea2e0dcdf891f30a5451b89f05737a6d693889e" } } ], "extra": [ 1, 4, 135, 11, 248, 57, 186, 78, 42, 229, 113, 121, 158, 147, 177, 72, 58, 235, 248, 208, 211, 143, 122, 205, 8, 64, 138, 198, 4, 110, 162, 116, 196, 2, 17, 0, 0, 0, 6, 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