Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e10c01298d358e79e46667f86538bc879132dbc6d45eb409f832c2810dd003

Tx prefix hash: 19642f8064dabd4ed4abe41f8f0bb15fd0cd3bf0e69d417f4421ad880ad3b445
Tx public key: c2e63c6c2b00cba0c1754464bdff4d5fcb426fb60e081c00f5f53be7f6bf032d
Timestamp: 1717300351 Timestamp [UCT]: 2024-06-02 03:52:31 Age [y:d:h:m:s]: 00:296:05:05:11
Block: 1035177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211685 RingCT/type: yes/0
Extra: 01c2e63c6c2b00cba0c1754464bdff4d5fcb426fb60e081c00f5f53be7f6bf032d021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec9df1f2c624bc768e2aa53406454e2632dd5d6e5bbccf12bf71dd0435607d22 0.600000000000 1503696 of 15

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": 1035187, "vin": [ { "gen": { "height": 1035177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec9df1f2c624bc768e2aa53406454e2632dd5d6e5bbccf12bf71dd0435607d22" } } ], "extra": [ 1, 194, 230, 60, 108, 43, 0, 203, 160, 193, 117, 68, 100, 189, 255, 77, 95, 203, 66, 111, 182, 14, 8, 28, 0, 245, 245, 59, 231, 246, 191, 3, 45, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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